home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
NT Sources
/
Infomagic - NT Source Volume 1 (Disc 1 of 2).iso
/
network
/
pcdctrla.exe
/
PCDCTRL.EXE
/
README.OS2
< prev
next >
Wrap
Text File
|
1998-01-23
|
33KB
|
859 lines
PC-Duo for OS/2
===============
Release Notes
=============
v3.72
=====
Copyright (c) 1997 PCI, Vector Networks Limited
All Rights Reserved.
Author : D. Briggs.
Revision Date : 20th January 1998
This document contains the release notes accompanying version 3.72 of the
NetSupport PC-Duo PC-PC Remote Control package for OS/2.
This software is supplied under a licence and may only be used or copied in
accordance with the terms of that licence. This software or copies thereof
must not be made available to unauthorised personnel.
No title to this software nor ownership of this software is hereby
transferred.
Evaluation copies are supplied for the purpose of evaluation only and
must not be resold or passed to any third party without the express
permission of Vector Networks Limited.
Please note that serial number files (CLIENT.SER) for versions earlier than
3.70 will not work with this release. Please contact your Supplier for a
new authorisation key if necessary.
Please ensure that you have adequate PC backup before you install PC-Duo.
Contents
========
1 Introduction
2 Package Enhancements over the Previous Release
2.1 OS/2 Support
2.2 New Well-Known TCP/IP Port Number
2.3 Request Help
3 Problems Corrected in this Release
4 OS/2 Support
4.1 Requirements
4.2 Limitations
5 Known Problems in this Release
5.1 DCAF-Enabled Video Drivers
5.2 PMCONFIG must run from the PCDUO Directory
5.3 NetBIOS Error 38
5.4 Fault in NBCTL.DLL
6 Installation Notes
6.1 Windows SETUP Hangs
6.2 Changes to OS/2 System Files
6.3 Sample OS/2 System Files
7 OS/2 Networking
7.1 Installing MPTS
7.2 Configuring MPTS
7.3 Configuring the Network Card Driver
7.4 IPX Networks
7.5 NetBIOS Networks
7.6 TCP/IP Networks
8 PC-Duo Remote Comms
8.1 Configuring the Bridge Programs
8.2 Dialling into a Standalone OS/2 Machine
8.3 Dialling into an OS/2 machine over IPX
8.4 Hiding the Standalone Windows Bridge Icon
9 Uninstalling PC-Duo
10 Diagnostic Utilities
11 Vector WWW Site
12 Feedback
1 Introduction
================
This document contains the release notes accompanying version 3.72 of the
NetSupport PC-Duo PC-PC Remote Control package for OS/2.
See Section 4.1 below for details of the software and hardware requirements
for correct operation. Section 4.2 contains information on the limitations
of this implementation.
This document is not intended as a replacement for the IBM manuals and help
files. It focusses on the problems that you are likely to experience while
getting PC-Duo running. It provides workarounds (highlighted with '**') for
bugs in IBM's installation and configuration programs. Some degree of
familiarity with OS/2 is assumed: You may need to edit CONFIG.SYS and/or
PROTOCOL.INI.
We recommend that you print this file, get yourself a cup of coffee, and
read it through before proceeding. The information in this file is more up
to date than the Windows PC-Duo Help or the printed manual.
2 Package Enhancements over the Previous Release
==================================================
See the PC-Duo Windows Help, New Features topic, for a complete description
of the enhancements provided in this release.
The following enhancements have been made since v3.60 was released:
2.1 OS/2 Support
----------------
This is the first release of PC-Duo to include support for OS/2. Note that
a special licence key is required to enable OS/2 support.
2.2 New Well-Known TCP/IP Port Number
-------------------------------------
Well-known TCP/IP port number 5405 has been allocated to PC-Duo. The Client
and Control default to this port instead of the previously used port 5000.
If necessary, the port number can be changed by adding an entry to file
WCONTROL.INI (in the PCDUO directory on the Client).
For example:-
[TCPIP]
port=5405
The v3.70 Control will try the port specified in an existing Known Clients
database entry first. If that does not work, it tries port 5405. Similarly,
if connecting to port 5405 fails, the Control tries port 5000 before giving
up.
2.3 Request Help
----------------
The Client can request assistance by pressing an SOS Hotkey combination or
by selecting the Request Help option from the Client's Commands Menu. The
request is sent immediately if a Control is already connected. If no
Control is connected, the SOS will be sent when a Control next connects to
this Client.
The default SOS Hotkey combination is ALT+LSHIFT+RSHIFT. Press the
left-hand ALT key, and hold it down while pressing the left- and right-hand
Shift keys. This is different to the Control's default hotkeys so as to
avoid a conflict when both Control and Client are running on the same PC.
The SOS Hotkey combination can be changed using the Configurator.
3 Problems Corrected in this Release
======================================
4 OS/2 Support
================
PC-Duo can be installed and used as a Windows Control and Client on OS/2
Warp versions 3 and 4. It should interwork with PC-Duo on DOS, Windows 3.1,
Windows for Workgroups v3.11, Windows 95, and Windows NT v3.50, v3.51, or
v4.0, over IPX/SPX, NetBEUI or any other compatible NetBIOS, or TCP/IP
Windows Sockets transports.
4.1 Requirements
----------------
PC-Duo requires OS/2 Warp 3 or later with Presentation Manager installed.
Warp 4 is recommended. IPX, NetBIOS, and TCP/IP Windows Sockets are
supported, but a suitable network configuration must be installed. See
Section 7.1 below for instructions on installing the OS/2 Multi-Protocol
Transport Services (MPTS).
The Windows Control also requires Win-OS/2 (and NetBIOS services if you
want to use a NetBIOS transport) to be installed. NetBIOS services can be
installed with MPTS.
In order for the Client to intercept display output, the display driver
must be "DCAF-enabled". See Section 5.1 below for more information.
4.2 Limitations
---------------
This is the initial release. Several functions are not available at this
time. These are:-
o Show has not been implemented in the OS/2 Windows Control or Client;
o The OS/2 Client cannot capture printer output for a connected Control,
though print capture from another Client to an OS/2 Control does work;
o Full-screen DOS, OS/2, and Windows sessions cannot be viewed;
o Colour depth is limited to 16 colours, regardless of the actual colour
depth setting at the Client. A viewing Control will map colours to the
nearest in the standard VGA pallette.
o The Client's cursor shape is not sent to the Control when the mouse is
over a Windows application;
o Colour cursors are displayed at the Control in monochrome;
o The DOS Bridge does not work.
OS/2 intercepts some keystrokes which makes it impossible for the Control
user to send them to the Client simply by typing them on the keyboard. The
Selected Client menu includes "Press and hold ALT" and "Send CTRL" options
to help get around this limitation.
5 Known Problems in this Release
==================================
5.1 DCAF-Enabled Video Drivers
------------------------------
The OS/2 Client requires a DCAF-enabled video driver. The following drivers
(as supplied with OS/2 Warp 3) are DCAF-enabled:-
o VGA;
o Cirrus Logic 543x;
o S3 801/805/928;
o S3 Trio 64V (as supplied with the OS/2 Warp Driver Pak V1.0, in
drivers\s3trio64v.zip)
You can use the VGA driver with all video cards.
The following drivers are known *not* to be DCAF-enabled:-
o Cirrus Logic 542x
o Weitek P9000 (as used in the Diamond Viper)
A driver for the S3 ViRGE chipset (which is used in the Diamond Stealth 3D
card) is available for download from the Diamond Multimedia web site
(www.diamondmm.com). This driver is DCAF enabled but it contains a bug that
causes the OS/2 Client to crash. This problem has been reported to Diamond
technical support.
5.2 PMCONFIG must run from the PCDUO Directory
----------------------------------------------
The OS/2 Client Configurator program, PMCONFIG, must be run from the
current directory and not from a directory on the PATH.
For example:-
cd \pcduo
pmconfig
5.3 NetBIOS Error 38
--------------------
This error can be reported during PC-Duo Client startup if the NetBIOS
configuration does not have enough name table space. This can be corrected
by increasing the NAMES definition in the relevant section of PROTOCOL.INI.
See the sample files in Section 6.3 below for examples.
5.4 Fault in NBCTL.DLL
----------------------
If the Control fails with a protection fault in NBCTL.DLL, try running it
in a full-screen Win-OS/2 session.
6 Installation Notes
======================
The PC-Duo Evaluation Kit is now supplied on three floppy disks or one
CD-ROM. DOS, OS/2, and Windows installations start with Disk-1. Disk-1
contains most of the software required for Windows installations. Disk-2
contains Windows NT software. Disk-3 contains OS/2 and DOS software, plus
various patches and test programs.
You should install the OS/2 Multi-Protocol Transport Services (MPTS) before
you install PC-Duo. MPTS installation is described further in Section 7.1.
Windows installation of Client and Control programs is started by running
SETUP.EXE from Disk-1. The OS/2 Client (only) can also be installed by
running INSTOS2.CMD from Disk-3. This does not require Windows.
Change disks when you are prompted to do so.
6.1 Windows SETUP Hangs
-----------------------
If Windows SETUP freezes, create a temporary directory on your hard disk.
Copy the contents of Disk-1 to -3 into it, and then run SETUP from there.
You can delete the temporary directory when installation is complete.
6.2 Changes to OS/2 System Files
--------------------------------
The Client installer adds the following lines to the end of CONFIG.SYS:-
rem NSM PC-Duo for OS/2 - PCIPDD.SYS
DEVICE=C:\PCDUO\PCIPDD.SYS
This assumes that you install into directory C:\PCDUO.
It also adds lines to start the Client at the beginning of STARTUP.CMD:-
For example:-
rem NSM PC-Duo for OS/2 - PMCLIENT.EXE
start C:\PCDUO\PMCLIENT.EXE /unb *
Windows SETUP creates a PC-Duo Windows Program Manager group containing
an 'Uninstall' icon (amongst other things) which reverses these changes.
To change settings after installation, run the "PC-Duo Configurator" icon
from Windows or PMCONFIG from OS/2.
6.3 Sample OS/2 System Files
----------------------------
The following extracts from working OS/2 system files might be of help if
you experience problems. These files include support for IPX, NetBIOS and
TCP/IP transports. OS/2 is installed on drive C:.
C:\CONFIG.SYS:
...
DEVICE=C:\IBMCOM\PROTOCOL\LANPDD.OS2
DEVICE=C:\IBMCOM\PROTOCOL\LANVDD.OS2
DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM /S
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
...
DEVICE=C:\NETWARE\VIPX.SYS
DEVICE=C:\NETWARE\VSHELL.SYS GLOBAL
...
DEVICE=C:\IBMCOM\MACS\SMC8000.OS2
REM --- NetWare Requester statements BEGIN ---
SET NWLANGUAGE=ENGLISH
DEVICE=C:\NETWARE\LSL.SYS
RUN=C:\NETWARE\DDAEMON.EXE
DEVICE=C:\IBMCOM\PROTOCOL\ODI2NDI.OS2
REM DEVICE=C:\NETWARE\ROUTE.SYS
DEVICE=C:\NETWARE\IPX.SYS
DEVICE=C:\NETWARE\SPX.SYS
RUN=C:\NETWARE\SPDAEMON.EXE
REM DEVICE=C:\NETWARE\NMPIPE.SYS
REM DEVICE=C:\NETWARE\NPSERVER.SYS
REM RUN=C:\NETWARE\NPDAEMON.EXE
DEVICE=C:\NETWARE\NWREQ.SYS
IFS=C:\NETWARE\NWIFS.IFS
RUN=C:\NETWARE\NWDAEMON.EXE
REM DEVICE=C:\NETWARE\NETBIOS.SYS
REM RUN=C:\NETWARE\NBDAEMON.EXE
DEVICE=C:\OS2\MDOS\LPTDD.SYS
REM --- NetWare Requester statements END ---
CALL=C:\IBMCOM\PROTOCOL\NETBIND.EXE
RUN=C:\IBMCOM\LANMSGEX.EXE
SET NLSPATH=C:\MPTN\MSG\NLS\%N;
SET ETC=C:\MPTN\ETC
DEVICE=C:\TCPIP\BIN\VDOSTCP.VDD
DEVICE=C:\TCPIP\BIN\VDOSTCP.SYS
RUN=C:\TCPIP\BIN\VDOSCTL.EXE
DEVICE=C:\MPTN\PROTOCOL\SOCKETS.SYS
DEVICE=C:\MPTN\PROTOCOL\AFOS2.SYS
DEVICE=C:\MPTN\PROTOCOL\AFINET.SYS
DEVICE=C:\MPTN\PROTOCOL\IFNDIS.SYS
RUN=C:\MPTN\BIN\CNTRL.EXE
CALL=C:\OS2\CMD.EXE /Q /C C:\MPTN\BIN\MPTSTART.CMD >NUL
DEVICE=C:\IBMCOM\PROTOCOL\NETBEUI.OS2
DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2
The PATH, LIBPATH, and DPATH statements should also contain the directories
listed in Section 7.1.
C:\NET.CFG:
Link Driver SMC8000
frame ethernet_802.3
protocol ipx 0 ethernet_802.3
C:\IBMCOM\PROTOCOL.INI (complete):
[PROT_MAN]
DRIVERNAME = PROTMAN$
[IBMLXCFG]
NETBEUI_nif = NETBEUI.nif
ODI2NDI_nif = ODI2NDI.NIF
TCPIP_nif = TCPIP.NIF
ETHOS2AT_nif = ETHOS2AT.NIF
[NETBIOS]
DriverName = netbios$
ADAPTER0 = netbeui$,0
ADAPTER1 = netbeui$,1
[NETBEUI_nif]
DriverName = netbeui$
Bindings = ETHOS2AT_nif
ETHERAND_TYPE = "I"
USEADDRREV = "YES"
OS2TRACEMASK = 0x0
SESSIONS = 254
NCBS = 255
NAMES = 29
SELECTORS = 15
USEMAXDATAGRAM = "NO"
ADAPTRATE = 1000
WINDOWERRORS = 0
MAXDATARCV = 4168
TI = 30000
T1 = 1000
T2 = 200
MAXIN = 1
MAXOUT = 1
NETBIOSTIMEOUT = 500
NETBIOSRETRIES = 3
NAMECACHE = 1000
RNDOPTION = 1
PIGGYBACKACKS = 1
DATAGRAMPACKETS = 10
PACKETS = 335
LOOPPACKETS = 8
PIPELINE = 5
MAXTRANSMITS = 6
MINTRANSMITS = 2
DLCRETRIES = 10
FCPRIORITY = 5
NETFLAGS = 0x0
[ODI2NDI_nif]
DriverName = odi2ndi$
Bindings = ETHOS2AT_nif
NETADDRESS = "I0000c07c7014"
TOKEN-RING = "NO"
TOKEN-RING_SNAP = "no"
ETHERNET_802.3 = "YES"
ETHERNET_802.2 = "YES"
ETHERNET_II = "YES"
ETHERNET_SNAP = "YES"
TRACE = 0x0
[TCPIP_nif]
DriverName = TCPIP$
Bindings = ETHOS2AT_nif
[ETHOS2AT_nif]
DriverName = SMC8000$
IOBase = 0x260
IRQ = 5
RamAddress = 0xD800
7 OS/2 Networking
===================
You are likely to have problems in this area. IBM has shipped a number of
different networking products for OS/2 over the years, and many of these
have overlapping or conflicting functionality. PC-Duo requires peer-to-peer
networking services. You may need to make some configuration changes (for
example to run over IPX even though you can already connect to a NetWare
server).
The following section describes how to set up OS/2 Multi-Protocol Transport
Services (MPTS) for use with PC-Duo. MPTS provides IPX/SPX, NetBIOS, and
TCP/IP support for OS/2, DOS and Windows programs. MPTS is available as a
separate product for Warp 3 and is 'in the box' with Warp 4. Make sure that
you have a version dated late 1995 or later.
These sections also contain information which should be useful to users of
older IBM or Novell networking products. MPTS can migrate Communications
Manager configuration files.
7.1 Installing MPTS
--------------------
On Warp 3, run the MPTS installer (INSTALL.CMD). For Warp 4, MPTS will be
installed when you install Warp (choose "Advanced installation" and specify
"File and print client", plus "TCP/IP services" for TCP/IP and/or "Netware
client" for IPX).
You run the PC-Duo OS/2 Client (PMCLIENT) on all OS/2 machines which are to
be remote controlled. The Client requires OS/2 networking services only.
You run the Windows Control (WCONTROL) on any machines which will be used
to remote control Clients, even if the Clients are also OS/2 machines. The
Windows Control requires Win-OS/2 to be installed, and networking services
for Win-OS/2 sessions must be operational.
MPTS sets up the following top-level directories:
IBMCOM: This contains NDIS protocol manager, MAC (card) drivers and NetBIOS
support. This is sometimes referred to as LAPS (Lan Adapter and Protocol
Services).
MPTN: This contains the MPTS configuration program (BIN\MPTS.EXE) and
'system level' TCP/IP support programs such as arp, route, inetcfg, ping
and so forth.
NETWARE: This contains IPX/SPX support and the NetWare requester.
TCPIP: This contains TCP/IP utilities, e.g. telnet, ftp, and also the
corresponding server daemons (e.g. telnetd, ftpd). It also contains DOS
support for TCP/IP.
Other directories (such as IBMLAN, IBM18N) may be created for other
network-based services such as file and print sharing. PC-Duo does not use
these.
MPTS puts the following directories on your PATH:-
x:\MPTN\BIN;x:\IBMCOM;x:\NETWARE
(where x: is the drive where you installed MPTS, normally C:)
MPTS puts the following directories on LIBPATH:-
x:\MPTN\DLL;x:\IBMCOM\DLL;x:\NETWARE;x:\NETWARE\NLS\ENGLISH
MPTS puts the following directories on DPATH:-
x:\MPTN;x:\IBMCOM;x:\NETWARE;x:\NETWARE\NLS;x:\NETWARE\NLS\ENGLISH
** Note that the MPTS installer does not always get the semi-colons in the
right place, so it's worth checking CONFIG.SYS manually.
7.2 Configuring MPTS
--------------------
MPTS is configured when you install it. You can change the configuration
after installation by running MPTS.EXE or by opening the "MPTS Network
Adapters and Protocol Services" icon in the "OS/2 System - System Setup"
folder.
Pressing the [Configure] button in the "Multi-Protocol Transport Services"
dialog will take you to the "Configure" dialog.
** The following files may need manual editing after MPTS configuration is
complete (see below for more details):
PROTOCOL.INI in \IBMCOM
NET.CFG in the root directory of your OS/2 drive
CONFIG.SYS in the root directory of your OS/2 drive
** You can press F1 when the cursor is in an entry field to get help on
that field.
7.3 Configuring the Network Card Driver
---------------------------------------
From the "Configure" dialog, select "LAN adapters and protocols" and press
[Configure]. This opens the "Adapter Protocol and Configuration" dialog.
Check that your network card appears in the "Current Configuration"
listbox, and that the required protocols are listed below it. If not, add
them from the listboxes above. The NE2000 driver is under "Eagle"!
Highlight the network card in the 'Current Configuration' listbox and press
[Edit]. Check that the I/O base address, Interrupt, and Shared RAM Address
correspond to your hardware settings.
** Note that for some cards (specifically the SMC 8000 series), MPTS does
not prompt you for the Interrupt and Shared RAM address, and you may need
to edit IBMCOM\PROTOCOL.INI manually to set these up. Look for a .TXT file
in IBMCOM\MACS (e.g. SMC8000.TXT), which explains how to do this. The
keywords you can use depend on the type of card you have.
** If you are using the Eagle NE2000 driver, you may need to change the
line in PROTOCOL.INI that reads:
DriverName = NE2000$ (or DriverName = NE200$)
to read:
DriverName = NE2000E$
You should do this if the driver reports that it "Can't find DriverName in
PROTOCOL.INI" when it loads during system startup.
** If you edit PROTOCOL.INI, you will need to edit it again every time you
run MPTS configuration.
If you only have one network card, you should not need to change any
adapter numbers.
7.4 IPX Networks
----------------
If you are using IPX/SPX, open the "LAN adapters and protocols" dialog,
highlight "IBM Netware Requester Support", and press [Edit]. Select the
desired frame type (all machines on the network should use the same frame
type). You can select more frame types if they are required by any other
software using the IPX stack.
** Edit NET.CFG to select the IPX frame type as follows.
For example:
Link Driver ETHOS2AT_nif
Frame Ethernet_802.3
Protocol IPX 0 Ethernet_802.3
Notes:
o This example uses frame type Ethernet 802.3;
o ETHOS2AT_nif is the name of the section in PROTOCOL.INI which loads
the Ethernet or Token Ring card. Copy this from the 'bindings='
statement in the [ODI2NDI_nif] section.
If you want to check that you've got this right, do *not* specify the frame
type in the MPTS configuration program. Then, when you add it to NET.CFG,
ODI2NDI will report the fact when it loads during system startup.
Other frame types supported by IPX include:-
o Frame Ethernet_802.2
Protocol IPX E0 Ethernet_802.2
o Frame Ethernet_II
Protocol IPX 8137 Ethernet_II
o Frame Ethernet_SNAP
Protocol IPX 8137 Ethernet_SNAP
o Frame Token-Ring
Protocol IPX E0 Token-Ring
o Frame Token-Ring_Snap
Protocol IPX 8137 Token-Ring_Snap
If more than one frame type is listed in NET.CFG, make sure that the one to
be used by PC-Duo is listed first.
** You may (or may not - see below) need to enter the MAC address of your
network card in "Network adapter address". Press F1 with the cursor in this
field for information. This address may be printed on the card, you may be
able to obtain it from the (DOS) utilities provided with the card, or you
may find it recorded in file \IBMCOM\LANTRAN.LOG.
If you have NetBIOS installed, the PMNBSTAT program supplied with PC-Duo
will report the address. Run PMNBSTAT /A0, and reverse the pairs of digits
it reports.
For example, if you have an Ethernet card and PMNBSTAT reports:-
address : 14 70 7c c0 00 00
Enter the following in the 'Network adapter address' field:-
I0000c07c7014
Some network cards allow you to avoid this if you move the statement which
loads the card driver in CONFIG.SYS so that it immediately precedes the
statement that loads LSL.
For example:-
...
DEVICE=C:\IBMCOM\MACS\SMC8000.OS2
DEVICE=C:\NETWARE\LSL.SYS
...
Look for the line containing SMC8000.OS2 in the sample CONFIG.SYS above.
We recommend that you try this first. Check file \IBMCOM\LANTRAN.LOG after
the system has booted. If this contains error LT80227, or if ODI2NDI or
PMCLIENT report the IPX address as FFFFFFFFFF, you will need to enter the
network card address manually as described above.
If you do edit CONFIG.SYS, you will need to edit it again every time you
run MPTS configuration.
** To run the Windows Control over IPX, ensure that TBMI2.COM is loaded in
AUTOEXEC.BAT, and NWIPXSPX.DLL is present in the WINDOWS\SYSTEM directory.
Ensure also that VIPX_ENABLED is set in the WIN-OS/2 settings for the
Windows session. The Windows Control reports "IPX not loaded or incorrectly
installed" or "Cannot find NSIPXSPX.DLL" if any of these conditions are not
met.
If you experience poor performance in the Windows Control, copy WSEND.EXE
from the TEST directory on Disk-3 into the same directory as the Control
program. Run WSEND /UIP, and measure the throughput when C)onnected to a
known good PC-Duo Client. The E)cho test should report 50 Kbytes per second
or more with 400 byte packets. If it does not not, check that your NetWare
drivers are dated 1995 or later (check the date of \NETWARE\NWCALLS.DLL).
Check also that your NETWARE\VIPX.SYS file is *not* dated 30-May-96, size
53248 bytes. This particular file appears to contain a bug. Files of the
same size but dated 19-Jan-96 and 30-Jul-96 are OK.
PC-Duo also runs correctly over Novell's NetWare Client for OS/2. This uses
ODI drivers instead of NDIS drivers and is easier to set up than the IBM
NetWare Requester (none of the above problems apply). Ensure that the frame
type is the same on all machines (set in NET.CFG as described above). You
can load the other protocols if you first load Novell's ODI-to-NDIS shim
(ODINSUP.SYS), but you have to set up CONFIG.SYS and PROTOCOL.INI manually.
PC-Duo expects IPX to use adapter number 0 (this is set in MPTS). PMCLIENT
can be configured to use a different adapter number by using the /A command
line option in STARTUP.CMD.
For example:-
START C:\PCDUO\PMCLIENT /UIP MY_PC /A1
The Windows Control always uses adapter number 0.
7.5 NetBIOS Networks
--------------------
If you are using NetBIOS, highlight "IBM OS/2 NetBIOS" in the "LAN adapters
and protocols" dialog and press [Edit]. You can accept the defaults, but if
PMCLIENT or PMNBSTAT report NetBIOS error 38, increase the "Maximum Names"
value by 4. This corresponds to "NAMES =" in the [NETBEUI_nif] section of
PROTOCOL.INI (see Section 5.3 above).
The "IBM OS/2 NetBIOS" is compatible with the Microsoft NetBEUI protocol
supplied with Windows for Workgroups, Windows 95 and Windows NT.
You can also install NetBIOS over IPX and NetBIOS over TCP/IP. Performance
is generally better when PC-Duo is using the raw protocols (i.e. IPX or
TCP/IP Windows Sockets).
You can run PMNBSTAT from the PCDUO directory to check NetBIOS adapter
numbers. You need to pass the desired adapter number to PMCLIENT via the /A
option if it is non-zero.
For example:-
START C:\PCDUO\PMCLIENT MY_COMPUTER /UNB /A1
PC-Duo does not use 'NetBIOS Socket Access'.
MPTS installs the required files to run the Windows Control over NetBIOS.
We have found that Warp 3 sometimes freezes when running NetBIOS
peer-to-peer applications. This appears to be an OS/2 bug. We solved it by
upgrading to Warp 4.
7.6 TCP/IP Networks
-------------------
For Warp 4, this is configured during installation if you install "TCP/IP
Services". Make sure that you specify at least your IP address and subnet
mask (normally 255.255.255.0).
Alternatively, select "TCP/IP Configuration" from the MPTS Configure
program "Configure" dialog, and press [Configure]. If the "TCP/IP
Configuration" radio button is disabled, run \TCPIP\BIN\TCPIPCFG.EXE
instead (TCPCFG.EXE in newer versions). This requests the same information
in workbook format. The details are not covered here.
Select "Network interface parameters" from the "TCP/IP Configuration"
dialog, and press [Configure]. Enter at least your IP address and subnet
mask.
Return to the "TCP/IP Configuration" dialog to set up router and Domain
Name Server addresses and the machine's hostname and domain name.
If you want the IP address to be displayed correctly in PMCLIENT's About
box, edit the hosts file (this will be either \MPTN\ETC\HOSTS or
\TCPIP\ETC\HOSTS, whichever is set in the ETC environment variable) and
ensure that there is an entry for the local machine's IP address and
hostname.
** MPTS does not appear to install TCP/IP for DOS support correctly. This
is required in order to run the Windows Control over TCP/IP.
If the Windows Control reports that it "Cannot find WINSOCK.DLL", copy this
file from \TCPIP\DOS\BIN to your WINDOWS\SYSTEM directory, or ensure that
\TCPIP\DOS\BIN is on the DOS PATH in AUTOEXEC.BAT. Check also that there
are no other WINSOCK.DLLs floating around that Windows might load by
mistake. If so, they are likely to generate other error messages, depending
on which WINSOCK is loaded.
If you get the message 'INETD not started', check that CONFIG.SYS contains
the following statements:-
DEVICE=x:\TCPIP\BIN\VDOSTCP.VDD
DEVICE=x:\TCPIP\BIN\VDOSTCP.SYS
RUN=x:\TCPIP\BIN\VDOSCTL.EXE
Here x: is the drive containing your TCPIP directory.
These should follow immediately after the 'SET ETC=...' statement.
8 PC-Duo Remote Comms
=======================
It is possible to use PC-Duo Remote Comms to dial into or out of an OS/2
system. Some additional steps may be required to configure OS/2 suitably.
8.1 Configuring the Bridge Programs
-----------------------------------
The PC-Duo OS/2 Client is able to load an IPX or NetBIOS Bridge program, in
much the same way as the normal Windows Client. This Bridge supports access
to other Clients on the local network, as well as other features such as
password-protection and dialback. These features can be configured using
the PC-Duo Configurator, provided Windows Setup was used to install the
Client. If the INSTOS2.CMD batch file was used to perform the installation,
then the Configurator may not have been installed, and the Bridge will have
to be configured by editing the START PMCLIENT line in STARTUP.CMD.
The Bridge command syntax is essentially identical to the Windows Client's
/BRIDGE and /NOBRIDGE command options. Refer to the User Manual or the
Windows PC-Duo Help for further information.
8.2 Dialling into a Standalone OS/2 Machine
-------------------------------------------
It is also possible to set up an OS/2 machine so that you can dial into it
without the machine being connected to a network.
To do this:
o Select "No network adapter" from the "Network Adapters" listbox in the
MPTS "Adapter and Protocol Configuration" dialog, and install IBM OS/2
NetBIOS support for it. Make a note of the adapter number that MPTS
assigns to it (or use PMNBSTAT, which reports a network address of all
zeroes for this adapter number).
o Load the PC-Duo OS/2 Client together with the /BRIDGE command option set
in STARTUP.CMD.
For example:
START PMCLIENT /UNB /BRIDGE COM1 /b38400 /MHayes-Compatible
o You should now be able to dial into the machine from a NetBIOS Remote
Control and connect to the Client. You will need to specify the adapter
number at the Control if it is non-zero (use the /Ax option).
8.3 Dialling into an OS/2 machine over IPX
------------------------------------------
Load the PC-Duo OS/2 Client together with the /BRIDGE command option set in
STARTUP.CMD.
For example:
START PMCLIENT /UIP /BRIDGE COM1 /b38400 /MHayes-Compatible
The "Standalone" configuration (/UIP /A) will not work. See Section 8.2 for
an alternative solution.
The IPX Bridge always uses IPX adapter number 0.
8.4 Hiding the Standalone Windows Bridge Icon
---------------------------------------------
If you are using the Standalone Windows Bridge (WSBRIDGE.EXE) instead of
the Client and Bridge DLL, you should not click on the running Bridge's
icon from the Control machine, as this will cause it to hang.
Alternatively, you can add /H to the WSBRIDGE command to hide the Bridge's
icon. If you do this, you can shut the Bridge down by running another copy
of WSBRIDGE with the /U command option.
9 Uninstalling PC-Duo
=======================
You do not normally need to uninstall or even stop an older version PC-Duo
Client before installing a new version.
We hope that you won't need to uninstall PC-Duo. Follow this sequence to
remove the software from your PC:-
Run the "Uninstall" icon from the PC-Duo group or folder. This will remove
the changes that SETUP made to CONFIG.SYS and STARTUP.CMD, and it will
delete the PC-Duo program group.
You can then delete the entire contents of the \PCDUO directory.
11 Diagnostic Utilities
========================
The following diagnostic programs are supplied with this kit. They can be
found on Disk-3, in the TEST directory.
\TEST\PMNBSTAT NetBIOS Adapter Status program for OS/2
\TEST\WSEND Windows network load test program
PMNBSTAT and WSEND programs can be used on OS/2. They are not installed by
Windows SETUP. Copy them into your PCDUO installation directory before use.
12 Vector WWW Site
====================
Visit our World Wide Web site for new product, software update, and release
information. Point your Web browser at one of the following URLs:
U.K. http://www.vector-networks.co.uk
U.S.A. http://www.vector-networks.com
13 Feedback
============
If you have any comments on the contents of this document, please send them
by e-mail to:-
support@vector-networks.co.uk
Thankyou for your assistance.